All of these fields (with the exception of region) is also available in backend properties. This is why we wanted to merge these 2 pages together, since this is duplicate information.

Right - so do you want me to add to each field the code to get it programmatically (some of it is in the first half of the page)? Or just state more clearly in the Platform section of this page, that you can also use Qiskit to find all of these?

Perhaps this page can be organized so that each section first introduces the data, then explain how to get that data from Qiskit / IQP. It'd be nice if we can have clickable tabs to show Qiskit vs IQP.

For example, we can have these sections

• Static QPU information
• Dynamic QPU information
• List and filter backends

And Static QPU information can say

Static QPU information

Some information about a backend does not change regularly, such as its name, version, the number of qubits it has, and the types of features it supports.

Native gates and operations

Each processor family has a native gate set. By default, the QPUs in each family only support running the gates and operations in the native gate set. Thus, every gate in the circuit must be translated (by the transpiler) to the elements of this set.

View with Qiskit | View on IQP (these are clickable tabs)

QPU versioning

...

And for the Dynamic QPU information section it'd just list out the attributes such as T1, T2, 2Q error, etc. Then clickable tabs to show how to find that data via Qiskit and IQP.

@jyu00 should I remove the headers "Qubit properties" and "Instruction properties", and just put them all together under Dynamic QPU info?